Brand voice is a system, not a style guide
Brand voice consistency doesn’t fail because of bad writing. It fails because most organizations treat voice as documentation instead infrastructure.
Brand voice consistency doesn’t fail because of bad writing. It fails because most organizations treat voice as documentation instead infrastructure.
While the wheels had been in motion for a little over a week, but Rubicon CX’s official first birthday is next week (January 23), but I had the time to do this today. With that in mind, I have some reflections to share about my first year of business in a most remarkable year in many ways.
As the entire planet struggles to come to terms with its new reality in the phase of the novel COVID-19 pandemic, I’ve begun to reflect a bit on the ramifications for what it is that we do. It would be very easy right now to pat ourselves on the backs and say something like “your content is now more important, blah, blah, blah”. But that’s not what I’ve been thinking about.
I spent a fair amount of time on SharePoint Modern projects in the last year of so, and you know what, I often found myself asking this same question. In the quest for easy implementation and out-of-the-box functionality, a lot is often left by the wayside. Look, I get it. Companies have to deal with limited budgets, and intranets or digital workspaces are generally low on their list of priorities, even though they tend to recognized their importance as a productivity tool.
A Newsweek blog has an interesting post describing how Obama’s branding efforts are more thorough and complete than any campaign thus far